Skip to content

docs: Add Nuxt 3 example for openapi-fetch #2331

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

HasutoSasaki
Copy link

@HasutoSasaki HasutoSasaki commented May 25, 2025

Changes

Add Nuxt example for openapi-fetch

How to Review

Docs change at the example section

Checklist

  • Unit tests updated
  • docs/ updated (if necessary)
  • pnpm run update:examples run (only applicable for openapi-typescript)

@HasutoSasaki HasutoSasaki requested a review from a team as a code owner May 25, 2025 07:56
@HasutoSasaki HasutoSasaki requested a review from gzm0 May 25, 2025 07:56
Copy link

netlify bot commented May 25, 2025

👷 Deploy request for openapi-ts pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 33a57a6

Copy link

changeset-bot bot commented May 25, 2025

⚠️ No Changeset found

Latest commit: 33a57a6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@gzm0
Copy link
Contributor

gzm0 commented May 27, 2025

Thank you very much for taking the time to contribute to openapi-fetch!

We are currently discussing among the maintainers whether we still want to increase the number of examples.
I realize the documentation actively invites new examples and in that sense is quite misleading. Apologies for that.

I have opened #2339 on which I hope we can discuss whether we should add more examples or not. Once we reach a decision there, I'll either proceed to review this PR or (unfortunately) reject it. (you are welcome to chime in in the discussion if you would like to).

@HasutoSasaki
Copy link
Author

@gzm0
Thank you for confirming!
We would be happy to participate in the discussion!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants